chore: add release workflow - #13
Merged
Merged
Conversation
|
This run was cancelled 🛑 The workflow was cancelled before completion. Please check the link below for details. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Adds a manual Release workflow mirroring orpc's, so publishing a new version is a single workflow dispatch instead of a local ritual. It validates the version input, bumps every workspace package, drafts a GitHub release, and publishes both packages to npm with provenance.
Workflow
workflow_dispatchwith a required version input plus optional dist-tag, skip-bump, skip-changelog, and skip-git-check flags.latestpreid before touching the repo.0.2.0-alpha.1publish under their preid tag by default; stable versions publish underlatest.packages/*only, so the root workspace package is never pushed to npm.Dependencies
bumppandchangelogithubadded as root dev dependencies, since the workflow runs them throughpnpm exec.Testing
pnpm run lintpasses with the new YAML file.bumpp -rdry run updated the root and both package manifests, then versions were reverted to 0.0.0.Before the first run
--provenancewithout an npm token, so@openapi-spec/typesand@openapi-spec/downgraderneed npm trusted publishing configured for this repo and workflow.